LFS crashes because of a problem with the ForceFeedback driver.
Only Scawen would be able to tell if the problem is with LFS.
You could try to re-install the driver for your wheel (check if a newer one is available at the website of the manufacturer).

Wow, nice idea and some great screenshots.

Quote from Nadeo4441 :

So GTA and CS:GO is for the unintelligent people? And you are part of a LFS master-race? Ironically, that's the stupidest thing I've read on this forum (and there's been a lot of stupid posts). It's just not your cup of tea, just like some people don't like simulations like LFS or AC. Calling people stupid for liking different games than you is insanely arrogant.

And by the way, I was hooked on LFS for a long time, all I could think about in school was LFS.. Like how I'm going to be playing it when I get home. And yes when I got cut off from it I was not happy. Doesn't matter what game, you can still get hooked on it.

Don't worry about cargame.nl, his only purpose of being here is to annoy and insult people.
Sad to see people like that around here, but I guess it's common now and happens on every online forum lately.

Hi, I made the follow piece of code a long time (2009) ago, so I guess that was for the then current version of Lapper.
But it might still work (sorry, not in the mood to go and try it) or you might be able to get it to work:

I think it kicks in as soon as the first car passes the first split.
While testing the code last night, nothing happened, until I finaly drove over the first split of Blackwood.

If you have a pc or server with LFS DCon running on, you can also put Lapper on it and let it run 24/7.
Nothing special has to be done for that.
Set it up, start it and leave it running.
That's how my server are done as well.

Last edited by Yisc[NL], Tue, 5 May 2015 08:55.

The code below does work.
Since !test is already used for something else, that might have caused your problem or the use of quotes, which isn't needed when using SetConfigVar.

If you know how to program, PRISM isn't hard.
So the main reason I struggle with it, is just because I don't know enough about programming.
Yeah, within Lapper I can find my way, but that's mainly buttons and storing/retrieving values etc.
I can code simple PHP-scipts used on websites, but PRISM is too complicated for me and it's lacking useful explanations and documented examples.

Last edited by Yisc[NL], Sun, 19 Apr 2015 17:00.

PRISM is way too complicated for most people.
Not that it shouldn't be included, but only very few can really use it.
Tried it myself recently and while I can do a lot with Lapper, I am totaly lost with PRISM.

IP address is enough to connect to it using RDP.
But then you also need a login and password to logon to the actual server.
I don't know how these official LFS servers work, so it might not be possible to control them like a normal server.
That's why AB.nl rents a VPS at a hosting company, so you have all the control over the machine.

But I guess you can connect to that server using RDP and if so, it would be easy to install Lapper on it.
Since Lapper doesn't require a regular installation, only unpacking the ZIP file, changing some values in the config files and start the executable.

Download Lapper and install it your self maybe?
Or don't you have access to such server using RDP and/or right to install anything?
Any LFS server can run Lapper, so the official ones won't be any different.

Could you explain a little bit more what you are trying to do?
Do you want to measure distance driven and then how fast someone breaks from 160 km/h to 0 km/h?

LFS Lapper is a program that uses the insim protocol to communicate with LFS.
Since all major communication with LFS is handled by Lapper, you only need to worry about creating buttons, store/retrieve values, etc to be done on certain events.
I have written a lot of scripts for Lapper (see Yisc's code release, https://www.lfs.net/forum/thread/84505-Yisc%27s-code-release) and only ran into a few things which aren't doable with Lapper or aren't working as the are supposed to work.

Then you haven't entered the correct login and password.
You need to enter the name and password you used when you bought the game.

Go to the unlock screen and enter your LFS account information (login and password) and it will unlock S2 on your pc.
You will have a maximum of 2 unlocks on your account and will get a new one every friday, in case the maximum of 2 isn't reached yet.

It's happening a lot lately that people post these kind of topic starters, with hardly any information and then expect others to help them.
What program did you use as a basis?
What is the code you currently have and isn't working?

Concerning point 1 and 2, I know that arrays got broken at some point and I am not sure that got fixed in a Lapper release. So some things regarding arrays might not work or not as intended. I might be able to help some more with it, but that would be tomorrow then.

Concerning point 3, I think the LFS Wiki is outdated.
This is what I read in Commands.txt , which is found in your "docs" folder of your LFS installation:

Autocross layout commands:

/axlist X :get list of layouts for track X - e.g. AU1
/axload X :load layout X on host
/axsave X :save layout X on host
/axlaps X :set autocross number of laps
/axclear :clear layout

Concerning point 4, I noticed the same behavior last night, so I think that is some LFS issue. It seems to correct it self, when you end the race, load the layout again and then start the next race.

I am still not convinced that the reason I gave last night, is the exact cause of the Finish/Result events not working, since Lapper does put your best time in the database when you cross the finishline, so it does know when you have finished. Will look into it again probably tomorrow.

Pfew, this puzzle nearly drove me nuts, but I found the answer at last.
For some reason, Lapper isn't recognizing the finishline used in the editor and therefor the OnFinish and OnResult event aren't activated.
To work around that issue (only a Lapper dev could answer that) you can use the following event to emulate an action on the finishline:


That event is called when you cross the finishline on a homemade layout.
I hope that works for you, as I am not sure all you could need, would be possible in that event.

Here's Lapper 6.0.14, which was the last version released by Kravy.
I will look into your issue a little later on, have to do some other things first.

*edit* forum doesn't allow me to upload a 2 MB zip file, so I have put it on my own webserver.

http://sjoerd.rosdorff.dyndns.org/test/lapper_6014.zip

Connected - V1.01 (tool to see who is connected to the server and inform players when to go to pitlane exit and start qualify, in case of oval races)

Pitboard - V2.09 (information screen about split times, gaps in front and behind you, ect)

Ctrack - V1.08 (tool to change the loaded track of an LFS server)


Change the extension of the files to .lpr and add them to addonsused.lpr to be able to use them.

To be able to use Ctrack properly, you also need an updated version of trackList.cfg which is also included in this message.
Change the extension to .cfg and put it in the bin-folder of Lapper.
Restart Lapper to activate the new file(s).

That message is caused by a part of the Pitboard script, in which you set the number of splits on a track.
To do so, type: !cfgsplits
Once that value is set, the Pitboard knows with how many sectors it should deal.

*edit* tonight I will release an update for Pitboard, Ctrack and Connected script, to coop with the recent LFS changes.

Last edited by Yisc[NL], Wed, 8 Apr 2015 07:30.

NCI before NCI?
That should probably be NCN before NCI.

Quote from Keling :

Quote from Yisc[NL] :

Processor: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz (8 CPUs), ~3.5GHz
Memory: 8192MB RAM
Card name: AMD Radeon HD 7900 Series
Display Memory: 4095 MB
Monitor Model: DELL U2713HM
Current Mode: 2560 x 1440 (32 bit) (60Hz)

What's wrong about that information?
I copied my specs from Dxdiag.
Here are screenshot taken from AMD Catalyst Control Centre and Dxdiag.